home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Tools (InfoMagic)
/
Internet Tools.iso
/
dos_win
/
winsock
/
maillist
/
94-05.Z
/
94-05
/
000363_support@netmanage.com_Wed May 25 04:01:58 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-05-31
|
16KB
Received: from relay1.UU.NET by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
id AB22399; Wed, 25 May 1994 14:26:38 -0400
Received: from netmanage.com (via netman-gate.netmanage.com) by relay1.UU.NET with SMTP
(5.61/UUNET-internet-primary) id AAwrlh06211; Wed, 25 May 94 14:26:29 -0400
Received: from suzannec.netmanage.com by netmanage.com (4.1/NetManage-1.0)
id AA07476; Wed, 25 May 94 11:18:14 PDT
Date: Wed, 25 May 94 11:01:58 PDT
From: support@netmanage.com
Subject: RE:Getting SLIP to work w\Chameleon
To: robinn@rpi.edu, winsock@sunsite.unc.edu, mckee@pacs.sunbelt.net
X-Mailer: Chameleon - TCP/IP for Windows by NetManage, Inc.
Message-Id: <Chameleon.4.00.4.940525112300.support@suzannec.netmanage.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Hello,
This should work if the script begins with a -n $r.
This skips an expect, then sends a carriage return. You can add additional
$r's for extra carriage returns
ie:
-n $r$r
We have a detailed document on slip/ppp setup with many scripting
examples below. Also, we do have a gopher server at "gopher.netmanage.com"
which is filled with helpful information for different Internet Providers for
slip/ppp dialup in the Third Party Vendors and Providers\Internet Providers
section.
Copyright 1993-4 NetManage Inc.
rev. 0003
Authors: Joseph I. Salamon
Using SLIP/CSLIP/PPP with Chameleon
INTRODUCTION
This document introduces the user to dial-up IP protocols, SLIP/CSLIP/PPP. In
this document the user will find basic SLIP/CSLIP/PPP information, hints for
writing a dial-up script, troubleshooting suggestions and recommendations.
This document also offers connection suggestions to an Internet Service
Provider.
GENERAL INFORMATION
SLIP and CSLIP are basically the same protocol, the major difference is the
header compression used by default in CSLIP packet format. The TCP
connection is faster when compressed header is used
PPP has the ability to negotiate several parameters such as: Header
compression and IP addressing. PPP is faster due to header compression and
bigger packets size transfers and provides enhanced security.
PPP packet size 1500 (top MTU) MTU - Maximum Transmission Units
SLIP/CSLIP packet size1006 (top MTU)
CHAP - special packet format for negotiation of security with PPP (supported
by NetManage PPP)
NetManage PPP is in PASSIVE mode for the first (3 sec). If NetManage PPP
does not receive any negotiation packet within first (3 sec), it will change
to the ACTIVE mode and start sending the negotiation packets
SLIP / PPP / CSLIP are 8bit protocols (currently Chameleon only support 8bit
login)
Dial-up Login (Internet Service Providers)
There are many companies which offer Internet connectivity, each provides a
different login procedure. To make things easier, NetManage offers dial-up
scripting capabilities. A user can write a simple script that will automate
the login procedure. Before connecting to an Internet Service Provider the
user must have access to the following information:
Type of connection (SLIP/CSLIP/PPP)
Phone number
UserName and Password
Local IP address (if not dynamically assigned)
Default Gateway IP address (IP address of the provider)
IP address for Domain Name Server (optional)
Mail Gateway, Mail Server and POP Server IP addresses (if Mail application
will be used) (optional)
Once the above information is available, you are ready to dial out.
User must add the above information to the Chameleon CUSTOM application.
When configuring the PORT settings in CUSTOM you must use:
8 Data Bits (other bit settings not supported currently)
1 Stop Bit
Parity none
NOTE: UserName field, of the CUSTOM Login menu, must be filled-in in order
for the dial-up script to be executed. If you are only required to send a
PASSWORD, you must have a dummy entry in the UserName field.
Writing Login/Connection script
The scripting language is used to negotiate the initial login to the remote
host. The remote host could be a UNIX box, a special SLIP/CSLIP/PPP router
like a NetBlazer, a Chameleon PC or a terminal server that supports the SLIP,
CSLIP or PPP protocols.
The scripting language is simply a series of alternating "Expect" and "Send"
statements. The "Expect" statements tell the script to wait for a series of
character(s) before it "Sends" a reply. The "Send" statements send the
information in response to a prompt (the preceding "expect") from the remote
host.
The script is kept in a file called SLIP.INI. For each SLIP,CSLIP or PPP
interface you create in Custom, an entry will be added to the SLIP.INI with
the name of the interface as a header.
There is a special character set used for writing a connection script. Please
refer to the Chameleon manual for the script character information.
EXAMPLE
If a user has defined both a SLIP and a PPP interface in the CUSTOM utility,
his/her SLIP.INI file will look something like this:
[DEFAULT]
SCRIPT=name: $u$r word: $p$r -n $6$c$r -i
TYPE=SLIP
[SLIP0]
SCRIPT=name: $u$r word: $p$r -n $6$c$r -i
TYPE=SLIP
[PPP0]
SCRIPT=name: $u$r word: $p$r -n $6$c$r -i
TYPE=PPP
Each new serial interface defined in CUSTOM will use the information under
[Default] as its initial default script. This script may need to be edited to
properly negotiate the login on a particular remote dial up host.
In order to successfully execute a dial-up script user must know the login
sequence. This means that the user must know the exact prompts, the order and
what needs to be sent at those prompts.
EXAMPLE
If you need to send a user name at the Login prompt, the script would look
like this:
SCRIPT=Login: $u$r
Login: - is the exact prompt to be expected (expects are case sensitive)
$u - will send the login name from the UserName field in CUSTOM
$r - will send a CR ( Carriage Return)
If you are not familiar with the exact login procedure do the following:
Connect to your Service Provider using windows terminal
Write down every Prompt, CR ( Carriage Return), and send parameter used.
EXAMPLE
Lets say that after you have connected using Windows terminal, before you can
send the UserName you need to send a Carriage Return (CR) (hit ENTER) to
"wake-up" the server. The script will look like this:
SCRIPT=-n $r Login: $u$r
-n Skip an expect. Anything following this character will be a send. In the
above example we are sending a CR represented by the $r character.
Lets take a look at the default script for interface [SLIP0]:
[SLIP0]
SCRIPT=name: $u$r word: $p$r -n $6$c$r -i
TYPE=SLIP
After the dial up is complete and the baud rate is negotiated the script
tells Chameleon to expect the characters "name:" contained in the initial
prompt from the remote host. After the prompt is received the program will
send the UserID (the $u parameter) and a Carriage Return ($r).
Next is an expect of the password prompt "word:". Even though the actual
prompt says "password:", you only need to put in the last 4 characters of any
prompt to create an "expect" string. After the prompt is understood by the
script, the script will send the value contained in the login PASSWORD field
in Custom and a CR ($p$r).
Then the script sends a 6 second delay ($6), the command to start SLIP,CSLIP
or PPP (represented by $c which sends the value specified in the Startup
Command field of CUSTOM application LOGIN menu), after skipping an expect
with the (-n) parameter. So the script reads -n $6$c$r immediately after the
password is sent.
The (-i) option at the end of the script, tells the system to expect an IP
address (an IP address displayed in text by the remote SLIP host). The (-i)
is not used for PPP. PPP negotiates the
addresses automatically.
SCRIPT EXAMPLE
Lets say that the remote device that the user is dialing into has
a (login:) prompt instead of the (name:), and no SLIP command.
The script will look like this:
[SLIP0]
SCRIPT=login: $u$r word: $p$r
TYPE=SLIP
A user can specify all of the send commands right in the script.
EXAMPLE
We have a UserID: Joe and the password: Chameleon
The script will look like this:
SCRIPT=login: Joe$r word: Chameleon$r
NOTE: Send strings separated by a space (two words or more) can not be send
from the script file and must be specified in the Startup Command field of
CUSTOM application.
NOTE: If the user is sending the parameters directly in the script file, the
user MUST specify something in the USERNAME field under the CUSTOM login
menu. If the USERNAME field is blank, the script will not be sent.
PROMPTING USERS for INFORMATION
You can also have the script prompt the user for UserName, password, etc..,
rather than having the script send them automatically. Inserting the $f
parameter into the script will bring up a dialog box that will allow you to
type the value in manually.
EXAMPLE
SCRIPT=login: $fEnter_Login$r
This script will prompt the user with a dialog box in Windows where the login
name can be entered. The text "Enter_Login" specifies the name of the dialog
box that will come up when the script encounters the $f parameter.
In the script, after the login prompt is received the dialog box named
"Enter_Login" will pop-up on the screen. The user will type in the user name
and hit the OK button.
Expecting an IP Address in SLIP/CSLIP (PPP negotiate IP addressing)
In some cases the remote server will returning a message like:
My IP address is xxx.xxx.xxx.xxx Your IP address is xxx.xxx.xxx.xxx
If you are using the " -i " option and expecting an IP address to be assigned
by the server, using the " -i " by it self will not work. The IP address
captured by the " -i " option will be first IP address found on this line,
which is the IP address of the server. In this case the user must put an
expect on the first IP address and use the " $- " option to skip all data
until the next IP address is located.
EXAMPLE
The system returns the following message:
My IP address is 157.27.1.1 Your IP address is 157.27.1.19
Using the above example, the script might look something like this:
SCRIPT=name: $u$r word: $p$r -n $6$c$r Your $- -i
In the above example we are using "Your" to set the first expect, then the "
$- " option used to skip to the next expect (in the above example it is
represented by the " -i " character). " -i " will find the next IP address.
SLIP/CSLIP/PPP ROUTING AND CONFIGURATION
When setting up a SLIP connection, verify that the local PC and the remote
device that user is dialing into (remote SLIP host) are on the same sub-net.
EXAMPLE
If the IP address of the remote SLIP host is 156.27.50.1 and the sub-net
mask is - 255.255.255.0 (a class B address subnetted 8 bits) then the local
PC's (HOST) IP address can be 156.27.50.2 with the
same sub-net mask.
Looking at the above example, you can see that local PC and the remote server
are located on the same sub-net.
If the remote SLIP host is a Chameleon PC with multiple interfaces (slip/ppp
and ethernet), then you must make sure that the SLIP/PPP and Ethernet
interfaces are configured on separate subnets.
EXAMPLE
Lets take a look at the following set-up:
SLIP/CSLIP/PPP Network
Ethernet network
(A)============================(B)(C)----------------------------------------
--------(D)
Local Host Chameleon PC w/modem
Remote Host
and Ethernet
card (Server)
In order to understand the addressing better, lets assign the IP address to
each of the devices on the sample network
(A) -- Local Host - 156.27.50.2 Sub-net mask - 255.255.255.0
(B) -- SLIP/PPP interface on the Server: 156.27.50.1 (Chameleon PC with
two interfaces defined)
Sub-net mask: 255.255.255.0
(C) -- Ethernet interface on the Server : 156.27.10.1 (Chameleon PC with
two interfaces defined)
Sub-net mask: 255.255.255.0
(D) -- Remote Host on the Ethernet network : 156.27.10.2
Sub-net mask: 255.255.255.0
In order to establish communication from device (A) to device (D)
Device (A) must have device (B) specified as its default gateway
and device (D) must know how to route back to the SLIP/CSLIP/PPP network via
device (C).
After addressing issues are resolved, verify the SLIP/PPP port settings in
the CUSTOM application (assuming that the user has defined SLIP, CSLIP or PPP
interface already).
Regards,
/\
**********/@@\ ****************************************
\__/ NetManage Inc.
W AA W Home of Chameleon TCPIP for Windows
|__AYA__/
AXXV Suzanne Calkins
VXXV Technical Support Representative
W VUV W (408)973-7171
|_/ V \_/ __ (408)973-8272 fax
\ [_ \ email: support@netmanage.com
\_____/ MIME enclosures are OK
gopher server: gopher.netmanage.com
******************************************************
---------------Original Message---------------
Return-Path: <winsock@SunSITE.Unc.EDU>
Received: from SunSITE.Unc.EDU (calypso-2.oit.unc.edu) by
mail.netmanage.com (5.0/SMI-SVR4)
id AA05640; Tue, 24 May 1994 19:46:54 +0800
Received: from (localhost.oit.unc.edu) by SunSITE.Unc.EDU
(5.65c+IDA/FvK-1.07) with SMTP
id AA05767; Tue, 24 May 1994 22:25:39 -0400
Errors-To: towfiq@sunsite.unc.edu
Date: Tue, 24 May 1994 22:25:39 -0400
Message-Id: <1994May24.220935.978@pacs.sunbelt.net>
Errors-To: towfiq@sunsite.unc.edu
Reply-To: mckee@pacs.sunbelt.net
Originator: winsock@sunsite.unc.edu
Sender: winsock@sunsite.unc.edu
Precedence: bulk
From: mckee@pacs.sunbelt.net
To: Multiple recipients of list <winsock@sunsite.unc.edu>
Subject: Re: anyone get SLIP to work with Chameleon??
X-Listprocessor-Version: 6.0a -- ListProcessor by Anastasios Kotsikonas
Content-Type: text
Content-Length: 952
In article <2rb73i$6o6@usenet.rpi.edu>, robinn@rpi.edu writes:
>
> I've been having the same problem. My SLIP server doesn't print any
> characters until a couple of carraige returns "wake it up." Then I start
> getting prompts. As far as I can tell, you can't do this with Chameleon.
>
>
> The difference is, this server obviously asks you for a "Username:" as
soon
> as you connect. The original poster and I share a problem in that our
> servers wait for a carraige return. Chameleon seems to get stuck if the
> first command is a "skip." (-n).
>
> If anyone has gotten something like this to work, please send me an
e-mail
> message. After this week I will no longer have an ethernet connection,
and
> unless I get a SLIP connection working, I won't be able to read news very
> easily.
>
> Thanks
>
> Nate Robinson
> robinn@rpi.edu
>
Key on the CONNECT message from the modem, wait 4 seconds, then send data.
tim mckee
----------End of Original Message----------
----------End of Original Message----------